Issue number: resolves #29705

What is the current behavior?

In a Vue tabs app, clicking the active tab button after landing directly on a tab child (browser refresh on /tabs/tab1/child, or browser back from an external window.location.href) is a silent no-op. IonTabBar.checkActiveTab only records the active tab's currentHref when there's a prevActiveTab, so the initial deep load leaves currentHref matching originalHref and the originalHref !== currentHref guard in IonTabButton.onClick skips resetTab. Even past that guard, resetTab issues router.go(routeInfo.position - currentHistoryPosition), which resolves to router.go(0) when the tab's only history entry is the current page.

What is the new behavior?

IonTabBar.checkActiveTab now records currentHref on initial setup so the tab state reflects the deep-loaded URL. resetTab takes the tab's originalHref and, when the first history entry for the tab is the current entry, falls back to handleNavigate(originalHref, "pop", "back", undefined, tab). The pop action routes through router.replace, so the deep-loaded child entry is replaced rather than stacked on top and no stale child entry stays in browser history.

Does this introduce a breaking change?

• Yes
• No

Other information

Manual test: /vue/tabs/tab1/childone. Load that URL directly, click the Tab 1 button, you should land on /vue/tabs/tab1